Repository navigation
build(ci): hand the weekly refresh PR off through a tracking issue - #405
Merged
Merged
Conversation
The org doesn't let GITHUB_TOKEN open PRs, so the first scheduled run pushed its branch and then failed. The workflow now commits the lockfiles through the API (GitHub-signed) and opens or updates an issue, assigned and mentioning the reviewers, with a one-click link to open the PR. Merging that PR closes the issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
avner-m
force-pushed
the
ci/deps-refresh-ci-token
branch
from
November 8, 2026 23:04
a70d43a to
48a0170
Compare
avner-m
marked this pull request as ready for review
November 8, 2026 23:10
dylan-paul
approved these changes
Nov 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The weekly dependency refresh now hands its PR off through a tracking issue instead of opening the PR itself.
scripts/deps/publish.mjs(new): commits the changed lockfiles todeps/weekly-refreshthrough the GitHub API, so the commit is signed by GitHub as before. It then opens or updates a "Weekly dependency refresh ready for review" issue containing the refresh report and a one-click link to open the PR. The link prefills the PR title and aClosesreference to the issue, so merging the PR closes the issue.ci-appsis dispatched so checks run on the new commit. When nothing changed, an open issue is closed.deps-weekly-refresh.yml: replaces thepeter-evans/create-pull-requeststep with the script. The issue is assigned toavner-mand mentions@avner-m @mattrglobal/labs-engs. Permissions are nowcontents: write,issues: write,pull-requests: read,actions: write.scripts/deps/publish.test.mjs(new): tests for the PR link and issue body.Why
The first scheduled run (2026-11-09) refreshed the lockfiles and pushed the branch, then failed at PR creation with "GitHub Actions is not permitted to create or approve pull requests". That setting is disabled at org level, and adding a token to a public repo isn't an option. Issues aren't covered by that setting, so the workflow stays automated up to the final click.
A side benefit: a PR opened by a person triggers
ci-appsthroughpull_requestas normal.Testing
node --test scripts/deps/*.test.mjs: 7 pass (3 new, 4 existing).workflow_dispatchand check that the branch commit shows as Verified, the issue is assigned and mentions the team, and the link opens a prefilled PR.🤖 Generated with Claude Code